--- In DynoMotion@yahoogroups.com, "geraldft" <geraldoft@...> wrote:
>
> Hi
>
> I was looking for info on this issue and found none, so thought I'd post my experiences so far, which may of use to others.
>
> Installation of Kmotion software is no problem, but drivers for Kflop require some manual intervention. The stock Kflop drivers are dated 2008 ver 2.4.6.0 so not certified for Windows7 X64.
>
> I downloaded the latest drivers from FTDI (www.ftdichip.com) - you need the D2xx drivers - version 2.08.14. Then to get them to install I had to copy the kflop.inf file from the old /USB driver folder into the equivalent folder of the new drivers. Then it's possible to update the old drivers or reinstall.
>
> Once I did this the Kflop seems to work fine along with the Kmotion administrative software...
>
> G
>

--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
>
> I have not checked the version, but I am able to run the default download on my win7x64 machine with no issues.
>
>
> I am interested to hear specifics on the problems you encountered in case they arise in the future.
>
> -Brad Murry
>

--- In DynoMotion@yahoogroups.com, "geraldft" <geraldoft@...> wrote:
>
> Hi Brad
>
> Thanks for your response. Actually I don't recall trying the older drivers - I just assumed I'd need the W7 64 bit drivers for this OS. Maybe some more testing will prove if there is any advantage, such as in speed of transfer or reliability perhaps.
>
> Where I did have a problem initially was with a program I wrote for the kflop using Visual Basic .net. When I compiled for "any CPU" or "x64" the program refused to work. At first I suspected it was because the kmotion dll's were 32bit and not compatible - since the error message pointed to this.
>
> But then I stumbled on some online discussion that indicated I should try compiling for X86 CPU - and lo and behold it then worked. Apparently if Win7 X64 sees a program which is compiled as X64 it expects the dll's to also be x64. But if you compile for X86 then it forces the OS to recognise them as 32 bit...
>
> BTW I notice you are writing some interface for C#. I'm curious if this offers significant advantages working with Kflop? Is it because you get more direct control of the internal functions this way? With VB.net I am restricted to the command set used by the kmotion console in combination with user c programs in the kflop.
>
> Regards Gerald Thompson
>
> --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> >
> > I have not checked the version, but I am able to run the default download on my win7x64 machine with no issues.
> >
> >
> > I am interested to hear specifics on the problems you encountered in case they arise in the future.
> >
> > -Brad Murry
> >
>

--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
> Hello Gerald
>
> You are correct, when using any win32 libs you must compile any .net assembly that will use that dll as x86. Note that if you have multiple projects in your solution that projects not utilizing the win32 libs do not need this restriction even if they use the projects that do use win32's.
>
> As far as the .net interface I have developed: It provides much more access to the Kflop functions. You have access to the console commands but you also get full CoordMotion access as we as complete G-Code Interpreter capabilities.
>
> You are not limited to using c# with it- you can use any CLR enabled language(VB.net, managed c++, c#, IronPython/IronRuby, etc...)
>
> It has been pointed out to me that commanding motions from the console scripts does not provide optimized motion profiles and therefore you will need to caclulate them yourself. Obviously when the motion paths are complex(mutltiple axes, many segments) you will see significant improvements when using the CoodMotion and it's underlying Trajectory Planner.
>
> As I said before, you can use it with VB.net just as if you were in c#. Download the source, compile it and ref the KMotion_dotNet.dll to your project. It is heavily documented with intellisense so hopefully most things will be self-explanatory.
>
>
> Let me know if you need any help.
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, "geraldft" <geraldoft@> wrote:
> >
> > Hi Brad
> >
> > Thanks for your response. Actually I don't recall trying the older drivers - I just assumed I'd need the W7 64 bit drivers for this OS. Maybe some more testing will prove if there is any advantage, such as in speed of transfer or reliability perhaps.
> >
> > Where I did have a problem initially was with a program I wrote for the kflop using Visual Basic .net. When I compiled for "any CPU" or "x64" the program refused to work. At first I suspected it was because the kmotion dll's were 32bit and not compatible - since the error message pointed to this.
> >
> > But then I stumbled on some online discussion that indicated I should try compiling for X86 CPU - and lo and behold it then worked. Apparently if Win7 X64 sees a program which is compiled as X64 it expects the dll's to also be x64. But if you compile for X86 then it forces the OS to recognise them as 32 bit...
> >
> > BTW I notice you are writing some interface for C#. I'm curious if this offers significant advantages working with Kflop? Is it because you get more direct control of the internal functions this way? With VB.net I am restricted to the command set used by the kmotion console in combination with user c programs in the kflop.
> >
> > Regards Gerald Thompson
> >
> > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > >
> > >
> > > I have not checked the version, but I am able to run the default download on my win7x64 machine with no issues.
> > >
> > >
> > > I am interested to hear specifics on the problems you encountered in case they arise in the future.
> > >
> > > -Brad Murry
> > >
> >
>